@mavarazy I know this package looks like it's not being maintained any longer but is it possible to get this PR merged and a new version pushed out? This just changes the npm version in the package.json because this package will no longer install in higher versions of npm if you have engine-strict=true set due to the "npm": "^2.14.7", setting. It's the only package out of the hundreds we use that has this problem and we would prefer not to fork and host our own version.

@mavarazy @Steffan-Ennis What's the process to get this merged and released? I don't see any labels or actions set up for the repo. Were you guys manually publishing this package? Should I bump the version in the package.json in this PR?

@mavarazy @Steffan-Ennis is it possible to get this merged? thanks in advance!